Gentlemen and Ladies, Quick history: I needed to remove & reinstall TCP-IP from my SBS2K3 SP1 machine in order to get a specific PPPOE device to work (Was being presented with that nasty "CP error 31" message) Subsequent to that, the machine is back up and running. File Access, ISA, etc are all operating fine. HOWEVER, when I try to use Outlook from any of my workstations, I am simply presented with the generic "Server Unavailable, 0x8004011D" error message in response to which I have tried removing profiles, recreating them, etc. all to no avail. You would ave to agree with me that this is a problem ON the server, as it occurs on every workstation and even new machines joined to the domain exhibit the same behaviour. Here is the kicker: Exchange IS is running Both PRIV and PUB Stores are mounted and accessible OWA and OMA works FINE. It is only when accessing the Exchange from specifically Outlook that it does not work. I have: Removed and Reinstalled Exchange 2003and all SPs Removed and Reinstalled ISA 2004 and all SPs Checked DCDIAG and NETDIAG, no errors reported Removed and Recreated a fresh IS And both the EventLogs on the server in addition to the EventLogs on the (mostly) WinXP client computers are squeaky clean, yet my problem persists and I am finally at my wits end. It's hard to troubleshoot an error when there is no apparent error (except that it does not work) Any ideas ? Where do I go from here ?

Hi Stephan, Please let me know: 1. How the Outlook connects to Exchange? Exchange method or POP3/SMTP? 2. When the error is encountered "Server Unavailable, 0x8004011D"? Send email, create profile (check name) or logon outlook? Mike

Hi Mike, All Outlook clients are connecting via Exchange method, not SMTP/POP3, I have also checked that I can connect to Prt 135 on the local LANIP without a problem The logon process gfoes as follows, Authentication Prompt -> Supply Credentials -> Credentials Accepted If you do not specify the Mailbox as default delivery location and instead specify a PST, Outlook will open, but as soon as you select the "Mailbox - User" you're prompted with a fairly non descript message stating the location could not be opened, that if it's on a server either access is denied, the sahre is unavailable or the server is down and that if it's a local OST or PST, you need to scan the files for integrity. Again throughout, the EventLogs remain squeaky clean and I havn't been able to find a switch to Outlook to enable debugging of sorts. HTH,

Hi Stephan, Would you please let me know whether the Outlook connects to Exchange server through RPC over Http? Or just RPC? Regarding the Outlook Logging, you can refer to following article: http://office.microsoft.com/en-us/outlook/HA011742661033.aspx Then, you can check application log on Outlook client for some information. Basically, we also need to analyze the etl file in the c:\Documents and Settings\user name\Local Settings\Temp folder for more information. Nevertheless, as the file is encrypted, you need to contact PSS to help you read the file. Therefore, I have provided some general methods for the issue: 1. Please disable Disable TCP Chimney and RSS features based on following article. Also update the NIC driver on the SBS server. Windows 2003 Scalable Networking pack and its possible effects on Exchange http://msexchangeteam.com/archive/2007/07/18/446400.aspx 2. Check the Registry key setting on the Server and troubleshoot some other connection issue by referring to following article: How to troubleshoot connectivity issues that are caused by RPC client protocol registry entries http://support.microsoft.com//kb/325930 Mike